翻訳と辞書 Words near each other ・ Acceptance (novel) ・ Acceptance and commitment therapy ・ Acceptance angle ・ Acceptance angle (solar concentrator) ・ Acceptance credit ・ Acceptance discography ・ Acceptance in lieu ・ Acceptance mark ・ Acceptance of evolution by religious groups ・ Acceptance of responsibility ・ Acceptance sampling ・ Acceptance set ・ Acceptance Speech ・ Acceptance Speech (Dance Gavin Dance album) ・ Acceptance Speech (Hip Hop Pantsula album) ・ Acceptance test-driven development ・ Acceptance testing ・ Acceptcard Pro Cycling ・ Accepted ・ Accepted and experimental value ・ Accepted Eclectic ・ Accepted Frewen ・ Accepted pairing ・ Acceptera ・ Acceptilatio ・ Acceptilation ・ Accepting house ・ Acceptor ・ Acceptor (semiconductors) ・ AccesRail Dictionary Lists mini英和辞書 mini和英辞書 Webster 1913 Latin-English FOLDOC Wikipedia English ウィキペディア

翻訳と辞書　辞書検索 [ 開発暫定版 ] スポンサード リンク Acceptance test-driven development ： ウィキペディア英語版 Acceptance test-driven development Acceptance Test-Driven Development (ATDD) is a development methodology based on communication between the business customers, the developers, and the testers. ATDD encompasses many of the same practices as Specification by Example,〔Adzic, Gojko. (2009) ''Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing'', Neuri Limited,〕 Behavior Driven Development (BDD),〔Chelimsky, David, Dave Astels, Zach Dennis, Aslak Hellesøy, Bryan Helmkamp, and Dan North. ''The RSpec Book: Behaviour Driven Development with RSpec, Cucumber, and Friends.'' The Pragmatic Bookshelf.〕 Example-Driven Development (EDD),〔(【引用サイトリンク】 Example Driven Design ) 〕 and Story Test-Driven Development (SDD).〔(【引用サイトリンク】 Story Test-Driven Development )〕 All these processes aid developers and testers in understanding the customer’s needs prior to implementation and allow customers to be able to converse in their own domain language. ATDD is closely related to Test-Driven Development().〔Beck, Kent. Test Driven Development: By Example. Addison-Wesley Professional, 2002.〕 It differs by the emphasis on developer-tester-business customer collaboration. ATDD encompasses acceptance testing, but highlights writing acceptance tests before developers begin coding. ==Overview== Acceptance tests are from the user’s point of view – the external view of the system.〔 They examine externally visible effects, such as specifying the correct output of a system given a particular input. Acceptance tests can verify how the state of something changes, such as an order that goes from “paid” to “shipped”. They also can check the interactions with interfaces of other systems, such as shared databases or web services. In general, they are implementation independent, although automation of them may not be.〔Melnik, Grigori, and Frank Maurer. (【引用サイトリンク】 Multiple Perspectives on Executable Acceptance Test-Driven Development )〕〔Koskela, Lasse. (2007) Test Driven: TDD and Acceptance TDD for Java Developers. Manning Publications〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Acceptance test-driven development」の詳細全文を読む スポンサード リンク 翻訳と辞書 : 翻訳のためのインターネットリソース Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.